Aqara: better temperature sensor for SRTS-A01 #10471
Conversation
switch `device_temperature` with `local_temperature`
|
Let's keep both to prevent a breaking change. |
|
done! |
|
thanks! |
|
I reverted this because it caused Nerivec/zigbee2mqtt-windfront#311, after taking a closer look it seems it was exposed twice (also with |
|
It is already exposed but only as part of the climate entity, which makes it not available as a sensor in itself. with the additional "standalone" without the change, it looks like this: without it, the sensor part is empty, and so if you want to use, let's say BetterThermostat, the only temperature sensor available is the Maybe my change is not the correct way to add it, so I'm open to suggestions, but I think the actual temperature should be available, and not through the climate entity, also because it is muxed behind "either this or an external sensor" What do you think? |
This reverts commit ea0355a.
2 participants
Aqara SRTS-A01 currently exposes
device_temperaturewhich I suspect is the microcontroller's internal temperature (usually a few degrees higher than the air temp, and only has 1° precision, whereas this one has 0.1°)The device also has
local_temperaturewhich seems to be the air temperature, and already is the measured temperature for the climate entity. this means thatlocal_temperatureis not exposed as a sensor. This fixes it.Potentially, we could keep both, but I'm not familiar enough with the dev of this project to make it clear which is which (if you keep both, you have 2 sensors exposed, and it's difficult to know which is which because they both are named temperature.)
Also, since local_temperature is only access.STATE, you have to wait until it is reported to get a value, so it might be unavailable on startup?
Open for suggestions